FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.7.16  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.ehrs.uv.phrsfmr2#current (47 ms)

Package hl7.ehrs.uv.phrsfmr2
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-PH.5.5.html
Url http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.5.5
Version 2.0.1-ballot
Status active
Date 2025-04-03T15:15:30+00:00
Name PH_5_5_PHR_Account_Holder_Configured_Alerts__Reminders__and_or_Notifications
Title PH.5.5 PHR Account Holder Configured Alerts, Reminders, and/or Notifications (Function)
Experimental False
Authority hl7
Description Alerts, reminders, and/or notifications are configured by the PHR Account Holder based on a variety of triggers or conditions.
Purpose The PHR Account Holder may desire to configure specific alerts, reminders, notifications, and/or notices (e.g., to promote compliance with physician orders, manage chronic conditions, perform routine health care measurements, or meet personal wellness goals). Note that the quantity, timing, or priority of such notices might also need to be configured. Example(s): The system SHOULD provide the ability to present medication recommendations based on findings related to a physician's diagnosis.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Statement N:

Alerts, reminders, and/or notifications are configured by the PHR Account Holder based on a variety of triggers or conditions.

Description I:

The PHR Account Holder may desire to configure specific alerts, reminders, notifications, and/or notices (e.g., to promote compliance with physician orders, manage chronic conditions, perform routine health care measurements, or meet personal wellness goals). Note that the quantity, timing, or priority of such notices might also need to be configured.

Example(s): The system SHOULD provide the ability to present medication recommendations based on findings related to a physician's diagnosis.

Actors:
ehr
Criteria N:
PH.5.5#01 SHOULD

The system SHOULD provide the ability to manage (e.g., by creating, capturing, correcting, updating) alerts, reminders, and/or notifications.

PH.5.5#02 SHOULD

The system SHOULD provide the ability to capture, maintain, and render configuration parameters regarding alerts, reminders, and/or notifications.


Source

{
  "resourceType" : "Requirements",
  "id" : "PHRSFMR2-PH.5.5",
  "meta" : {
    "profile" : [
      "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Alerts, reminders, and/or notifications are configured by the PHR Account Holder based on a variety of triggers or conditions.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The PHR Account Holder may desire to configure specific alerts, reminders, notifications, and/or notices (e.g., to promote compliance with physician orders, manage chronic conditions, perform routine health care measurements, or meet personal wellness goals). Note that the quantity, timing, or priority of such notices might also need to be configured.</p>\n<p>Example(s): The system SHOULD provide the ability to present medication recommendations based on findings related to a physician's diagnosis.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.5.5#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage (e.g., by creating, capturing, correcting, updating) alerts, reminders, and/or notifications.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.5.5#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture, maintain, and render configuration parameters regarding alerts, reminders, and/or notifications.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
  },
  "extension" : [
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode" : "ehr"
    }
  ],
  "url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.5.5",
  "version" : "2.0.1-ballot",
  "name" : "PH_5_5_PHR_Account_Holder_Configured_Alerts__Reminders__and_or_Notifications",
  "title" : "PH.5.5 PHR Account Holder Configured Alerts, Reminders, and/or Notifications (Function)",
  "status" : "active",
  "date" : "2025-04-03T15:15:30+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Alerts, reminders, and/or notifications are configured by the PHR Account Holder based on a variety of triggers or conditions.",
  "purpose" : "The PHR Account Holder may desire to configure specific alerts, reminders, notifications, and/or notices (e.g., to promote compliance with physician orders, manage chronic conditions, perform routine health care measurements, or meet personal wellness goals). Note that the quantity, timing, or priority of such notices might also need to be configured.\r\n\r\nExample(s): The system SHOULD provide the ability to present medication recommendations based on findings related to a physician's diagnosis.",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-PH.5.5-01",
      "label" : "PH.5.5#01",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to manage (e.g., by creating, capturing, correcting, updating) alerts, reminders, and/or notifications."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-PH.5.5-02",
      "label" : "PH.5.5#02",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to capture, maintain, and render configuration parameters regarding alerts, reminders, and/or notifications."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.